-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dnd: computeDrop hover.atTop check #199
Conversation
255b91c
to
7e58836
Compare
This is great. I'm pulling your branch now to run the tests. |
I think this is a bug. If a folder is open and has children you should not be able to place an item as the folder's sibling unless you drag it to the bottom of it's child list. Area.mp4 |
We could check if the above node isOpen and hasNoChildren, then allow the drop as sibling. Would that work for you? |
Awesome! That's the check I've been missing. I've updated with 9bcbf67. Do you think you had something like this in mind? |
Ship it! :D |
9bcbf67
to
c9af3ab
Compare
Yeah that is what I was thinking. I'll run my own tests again. Let's ship today. |
Based off #199 Thanks to the understanding and work of @edimov, we can now drop a node as a sibling (or child) of an open, but childless node. This should unlock people who want to create trees where every single node is an open, internal node. Co-authored-by: Evgeni Dimov <[email protected]>
Merged in #202 |
Description
This MR:
hover.atTop
check to allow siblings drop on nodes with empty childrencomputeDrop
calculations when hovering over same nodeScreenshots
Before
Screen.Recording.2023-12-09.at.20.42.11.mov
After
Screen.Recording.2023-12-09.at.21.23.53.mov